This can be also approached as a wrapper without touching nixpkgs, though perhaps with a little worse performance – a function that imports nixpkgs and recursively adds the attribute everywhere (all is lazy, of course). Something similar is done in ./maintainers/scripts/rebuild-amount.sh but the aim is different there.

Also recurseIntoAttrs is an ugly name. Something like enableAllPackages would be more descriptive.

@vcunat @edolstra regardless of the recurseIntoAttrs hackery, what about the new metric? Would you merge that if I split in into a separate PR?

The problem with #38635 (comment) is that hydra metrics graphs like memory consumption and etc don't make too much sense without knowing the number of packages it tried to evaluate.

ping. The metric thing was merged in #49863. What can be done to have the rest merged? Is the config option name the only problem here?

This is pretty useful for measuring massive changes like #50643.

The last commit was merged as #49863. The first commit now has a separate PR #56105.

should this be rebased or closed now?

My opinion on naming:

• recurseIntoAttrs should be called hydraPackageSet :: Attrset -> Attrset
• dontRecurseIntoAttrs should be called packageSet :: String -> Attrset -> Attrset
• recurseIntoAttrsMaybe should be called packageSet. Can you provide an insight on why some are "dont", and others are "maybe"? Is "all" your personal choice of "interesting" attrsets?

Also, a minor nitpick, I can suggest the following refactor to propagate package set name automatically:

inherit (lib.mapAttrs packageSet {
  nodePackages_10_x = callPackage ../development/node-packages/default-v10.nix { };
  nodePackages_8_x = callPackage ../development/node-packages/default-v8.nix { };
  nodePackages = nodePackages_8_x;
})
  nodePackages_10_x
  nodePackages_8_x
  nodePackages
;

Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the
   related code and @ mention them in a comment.
2. Ask on the NixOS Discourse. 3. Ask on the #nixos channel on
   irc.freenode.net.

I marked this as stale due to inactivity. → More info